System and method for tracking a line rate utilization

ABSTRACT

A system and method for tracking a line rate utilization. An effective throughput is measured for a data stream during a time period. A number of frames in the data stream is counted during the time period. A line rate utilization is determined for the data stream utilizing the number of frames and a size of the frames in response to the time period ending. The line rate utilization is save for communication to one or more users. The line rate utilization is communicated to one or more users.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation-in-Part of U.S. patent application Ser. No. 12/641,196, filed on Dec. 17, 2009, which is a Continuation-in-Part of U.S. patent application Ser. No. 12/412,127 filed on Mar. 26, 2009; Ser. No. 12/412,141, filed on Mar. 26, 2009 now U.S. Pat. No. 7,978,628; and Ser. No. 12/381,673 filed on Mar. 12, 2009 now U.S. Pat. No. 7,983,189, each of which claim priority to U.S. Provisional Patent Application Ser. No. 61/138,471, filed on Dec. 17, 2008, all of which are incorporated herein by reference.

BACKGROUND

The use of and development of communications has grown nearly exponentially in recent years. The growth is fueled by larger networks with more reliable protocols and better communications hardware available to service providers and consumers. In particular, an Ethernet local area network (E-LAN) service type may be used to create a broad range of services. E-LAN service types may be utilized based on one or more service level agreements (SLA) for a multipoint service.

The SLAs or other contractual obligations may specify guaranteed or acceptable thresholds for bandwidth, throughput, frame loss ratio, and other performance metrics, characteristics, or factors between customers and service providers. In many cases, the applicable communications network may include any number of service providers, access providers, legs, customers, and other elements that may complicate tracking performance or compliance for users or customers. The performance metrics are useful for trouble shooting, fault isolation, performance management (PM) threshold crossing, error identification, and other measurements that may not be shared between the many separate parties.

SUMMARY

One embodiment provides a system and method for tracking a line rate utilization. An effective throughput may be measured for a data stream during a time period. A number of frames in the data stream may be counted during the time period. A line rate utilization may be determined for the data stream utilizing the number of frames and a size of the frames in response to the time period ending. The line rate utilization may be save for communication to one or more users. The line rate utilization may be communicated to one or more users.

Another embodiment provides a system tracking a line rate utilization. The system may include a user network interface (UNI) and a network. The UNI may be operable to communicate with multiple UNIs. The network may be operable to communicate packets between the UNI and multiple UNIs. The UNI may include a port operable to measure an effective throughput for a data stream during a time period, count a number of frames in the data stream during the time period, determine a line rate utilization for the data stream utilizing the number of frames and a size of the frames in response to the time period ending, save the line rate utilization for communication to one or more users, and communicate the line rate utilization to one or more users.

Yet another embodiment provides a port operable to track a line rate utilization. The port may include a processor for executing a set of instructions and a memory in communication with the processor. The memory may be operable to store the set of instructions. The set of instructions may be executed to measure an effective throughput for a data stream during a time period, count a number of frames in the data stream during the time period, determine a line rate utilization for the data stream utilizing the number of frames and a size of the frames in response to the time period ending, save the line rate utilization for communication to one or more users, and communicate the line rate utilization to one or more users.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described in detail below with reference to the attached drawing figures, which are incorporated by reference herein and wherein:

FIG. 1 is a pictorial representation of a communications system implemented in accordance with an illustrative embodiment;

FIG. 2 is a pictorial representation of an E-LAN service type utilizing multipoint-to-multipoint Ethernet virtual connections (EVCs) in accordance with an illustrative embodiment;

FIG. 3 is a state diagram of SLA states in accordance with an illustrative embodiment;

FIG. 4 is a state diagram of SLA states in accordance with an illustrative embodiment;

FIG. 5 is a pictorial representation of nodes in a network in accordance with an illustrative embodiment;

FIG. 6 is a pictorial representation of a flowchart of a process for determining whether losses within a network comply with a SLA in accordance with an illustrative embodiment;

FIG. 7 is a pictorial representation of a network ring in accordance with an illustrative embodiment;

FIG. 8 is a pictorial representation of a flowchart of a process for determining whether losses within a network comply with a SLA for core throughput in accordance with an illustrative embodiment;

FIG. 9 is a pictorial representation of a network performance system in accordance with an illustrative embodiment;

FIGS. 10 and 11 are pictorial representation of bandwidth tables in accordance with illustrative embodiments;

FIG. 12 is a pictorial representation of a packet in accordance with an illustrative embodiment;

FIG. 13 is a graph illustrating throughput based on frame size in accordance with an illustrative embodiment; and

FIG. 14 is a flowchart of a process for determining line rate utilization in accordance with an illustrative embodiment.

DETAILED DESCRIPTION OF THE DRAWINGS

Illustrative embodiments provide a system and method for determining line rate utilization for determining technical or legal compliance with standards. Certain illustrative embodiments may be embodied in hardware, software, firmware, or a combination thereof. In one embodiment, bandwidth measurements and other performance metrics may be monitored by logic engines, devices, or other elements to suppress alarms during specific conditions when the alarms are not intended to be activated. Certain illustrative embodiments may be utilized to determine whether a multipoint SLA is being met without performing stress testing that may adversely affect the system or service. Certain illustrative embodiments may also determine whether frame loss or frame loss ratio (FLR) is acceptable or unacceptable according to the terms of a SLA.

Information regarding performance, state, and SLA compliance may be utilized by one or more embodiments of the present invention to determine that rate limiters or bit shapers have not sufficiently limited data traffic in a system to account for potential situations or inherent limitations. As a result, line rates have exceeded the sustainable throughput levels of the applicable ports or devices. Certain illustrative embodiments may utilize a static bandwidth profile or a dynamic bandwidth profile that accounts for different frame sizes to determine maximum throughputs, thresholds, and parameters that may be utilized to determine whether the SLA is compliant.

Two “normal” congestion states may occur in a multipoint service. The first congestion state is congestion experienced through the UNI (User Network Interface) egress point (hereafter “egress congestion” or “UNI congestion”) and the second is the congestion experienced with the core network service allocated bandwidth. UNI egress congestion may occur within multipoint services because the ingress of each port is “over-subscribed” based on the fact that multiple end-points (other UNI's) may coincidentally transmit traffic to a single destination UNI at one given time. In other words, multiple UNIs may communicate with a single UNI simultaneously. This creates an increased likelihood of congestion for multipoint services. As a result of such congestion at such a UNI egress point, point-to-point performance data may incorrectly show congestion between two points despite the fact that there is no congestion on the remainder of network services. To correctly characterize the multipoint service for purposes of reporting service level performance to customers, the performance information regarding congestion at any UNI egress point during the congestion period should be removed for more accurate SLA tracking.

The second congestion state is congestion experienced through a segment of a network used by more than one customer, such as a segment of a core network (hereafter “core congestion”). This may occur with special services and is useful when the SLA contains a “backbone” or global bandwidth limitation. In this case, the ability to transmit from all UNI ports at one time is restricted to a global amount of bits per second. This limitation may introduce a known and expected congestion state for the service. To effectively track the multipoint service using point-to-point frame loss or other performance criteria, the “congestion state” of the backbone network may need to be independently tracked. Similarly, the performance metrics for the backbone network may need to be removed from the SLA metrics to effectively characterize the network service being offered according to a particular SLA.

In one embodiment, a method may be embodied in a set of instructions stored within a memory and executed to determine compliance or non-compliance with a particular SLA. Certain illustrative embodiments may be utilized for unicast or multicast traffic. Certain illustrative embodiments may be utilized to track the state of performance and devices within communications networks and systems. In one embodiment, certain illustrative embodiments may be used to resolve SLA issues between service providers, operators, customers, and other users. In particular, certain illustrative embodiments may be utilized to display, track, and store information, data, and empirical evidence of SLA compliance and noncompliance across any number of parties, devices, or elements.

FIG. 1 is a pictorial representation of a communications system implemented in accordance with an illustrative embodiment. The communication system 100 of FIG. 1 includes various elements that may be used for wireless and wired communication. The communications system 100 may include a communications network 102, a communications management system 104, a server 106, UNIs 108, 110, and 111, customer premise equipment (CPEs) 112, 114, and 115, and intermediary devices 116 and 118. The communications system 100 may include any number of these elements, devices, components, systems, and equipment in addition to other computing and communications devices not specifically described herein for purposes of simplicity. For example, the communications system 100 may include various rate limiters or bit shapers. The different elements and components of the communications system 100 may communicate using wireless communications, such as satellite connections, WiFi, WiMAX, CDMA wireless networks, and/or hardwired connections, such as fiber optics, T1, cable, DSL, high speed trunks, and telephone lines.

Communications within the communications system 100 may occur on any number of networks which may include wireless networks, data or packet networks, cable networks, satellite networks, private networks, publicly switched telephone networks (PSTN), communications network 102, or other types of communication networks. The communications network 102 is an infrastructures for sending and receiving messages and signals according to one or more designated formats, standards, and protocols. The networks of the communications system 100 may represent a single communication service provider or multiple communications services providers. The features, services, and processes of the illustrative embodiments may be implemented by one or more elements of the communications system 100 independently or as a networked implementation.

In one embodiment, the communications network 102 is a Metro Ethernet network (MEN). Metro Ethernet network is a computer network based on the Ethernet standard and covering a metropolitan area. A Metro Ethernet network may be used as a metropolitan access network to connect subscribers and businesses to a wider area network, such as the Internet. Certain illustrative embodiments may be implemented utilizing any number of packet based networks or services, such as E-LAN or VLAN.

In one embodiment, an E-LAN service type may provide a best effort service with no performance assurances between the UNIs 108, 110 and 111. The UNIs are the physical and electrical demarcation point between the user and the public network service provider. In one embodiment, the UNIs 108, 110 and 111 connect a MEN from the CPEs 112, 114 and 115.

In another embodiment, the communications service or E-LAN service type may include performance assurances, characteristics, thresholds, parameters, and information between UNIs 108, 110 and 111, such as a committed information rate (CIR). CIR is a specified amount of guaranteed bandwidth. Other performance information may include a committed burst size (CBS), an excess information rate (EIR) with an associated excess burst size (EBS), delay, delay variation, loss, and availability for a given class of service (CoS) instance. For example, EIR may be a throughput performance management that tracks all transmitted and received frame octets.

In another example, CIR may be a service performance management of conforming traffic that represents the frame loss threshold used to determine if the service is conforming to the SLA. In one embodiment, the performance guarantees are included in an SLA. The SLA specifies the communications guarantees, thresholds, and actions that are agreed to by the communications service provider and a user/customer. Each of the UNIs 108, 110 and 111 may have a specified bandwidth CIR.

Configurations, such as multipoint communications, may introduce natural conditions, such as oversubscription. Bandwidth congestion states may result under and SLA when multiple UNIs communicate with a single UNI simultaneously. Frame loss may be fully acceptable when a UNI is at the specified CIR, indicating the user or customer is breaking the boundary or threshold of allowable service.

In one embodiment, the CPEs 112, 114 and 115 may be routers. In another embodiment, the UNIs 108, 110 and 111 may be switches or other intelligent network devices. The UNIs 108, 110 and 111, the CPEs 112, 114, and 115, the server 106 and other computing and communications devices within the communications network system 100, which may include busses, motherboards, circuits, ports, interfaces, cards, connections, leads, transceivers, displays, antennas, and other similar components. The UNIs 108, 110 and 111, the CPEs 112, 114 and 115, and the server 106 may further include a processor and memory as well as other communications and computing elements including, but not limited to busses, circuits, cards, boards, ports, caches, buffers, power supplies, drives, and other components. In one embodiment, certain illustrative embodiments may be implemented by instructions stored within the memory. In another embodiment, the logic may be integrated, programmed, or stored within a circuit, chip, or card.

The processor is circuitry or logic enabled to control execution of a set of instructions. The processor may be a microprocessor, digital signal processor, central processing unit, application specific integrated circuit, or other device suitable for controlling an electronic device including one or more hardware and software elements, executing software, instructions, programs and applications, converting and processing signals and information, and performing other related tasks. The processor may be a single chip or integrated with other computing or communications elements.

The memory is a hardware element, device, or recording media configured to store data for subsequent retrieval or access at a later time. The memory may be static or dynamic memory. The memory may include a hard disk, random access memory, cache, removable media drive, mass storage, or configuration suitable as storage for data, instructions, and information. In one embodiment, the memory and processor may be integrated. The memory may use any type of volatile or non-volatile storage techniques and mediums. In one embodiment, the memory may store the performance management information, data, and states that are determined and tracked as herein described. The memory may include any number of databases for tracking transmitted and received packets from one or more UNIs, nodes, maintenance entities, or other devices, elements, or modules.

As described, the UNIs 108, 110 and 111 may determine whether the terms of an SLA are being met utilizing congestion states, dynamic bandwidths, and throughput comparisons. The UNI congestion and core congestion may be utilized to analyze SLA compliance or noncompliance as well as generation of relevant alarms.

FIG. 2 is a pictorial representation of a communication system utilizing multipoint-to-multipoint Ethernet virtual connections (EVCs) in accordance with an illustrative embodiment. The communication system 100 is one embodiment of an E-LAN service type. The communication system 200 may include a MEN 201, and UNIs 202, 204, 206, and 208.

In various embodiments, such as the multipoint configuration of FIG. 1, measuring the CIR performance may be difficult. The difficulty may result from communications or inter-connectivity between the UNIs 202, 204, 206, and 208. UNIs 202, 204, 206, and 208 function as or are matched with one or more customer side UNI (UNI-C) and network side UNIs (UNI-N). The communication system may further include one or more network to network interfaces (NNIs), which may include external NNIs (E-NNI) and internal NNIs (I-NNI). Performance measurements and determinations of the illustrative embodiments may be performed by frame, bits, or packet counters or other devices at the port level of one or more communications devices within the communication system 100, which may also include the UNIs 202, 204, 206, and 208.

The communication system 100 illustrates one example of a shared bandwidth service in which the UNIs 202, 204, 206, and 208 may contend for bandwidth to communicate with each other. The communications service provider operating the MEN 201 may define a known bandwidth profile for each of the UNIs 202, 204, 206, and 208 which may include a bandwidth commitment. The bandwidth commitment may not be statically assigned to any specific UNI pair. As a result, using a single or even multiple UNI-to-UNI CIR bandwidth performance measurements may not be adequate to measure the parameters of the SLA agreed to by the communications service provider and the user.

In some cases, the communications service provider may guarantee bandwidth between legs of the service. The legs are connections between one or more UNIs. A guarantee between any two legs of the services reflects a core CIR. The SLA may provide guarantees for the core network, individual legs, and other point to point communications. In order to conform with the SLA, any of the UNIs 202, 204, 206, and 208 may be required to transmit (i.e. tx) and/or receive (i.e. rx) a throughput CIR. In some cases traffic contentions (i.e. multiple UNIs communicating with a single UNI simultaneously) may result in frame loss because of the contention for the shared bandwidth. If a frame loss ratio is utilized as a SLA indicator, the amount of bandwidth frames that may be communicated without contention is significantly smaller than the full bandwidth profile. Certain illustrative embodiments provide a system and method for addressing contention problems to individual UNIs, across legs, or through the network.

In one example, a communications service provider may sell service to four customers as represented by the UNIs 202, 204, 206, and 208. The SLA with each of the customers may guarantee an amount of bandwidth to each customer UNI, such as 1 Gb/second. However, problems result when the customers are communicating with one another at the same time. A SLA measurement for monitoring is performed in order to determine compliance. Communication between customers occurs frequently and could be web traffic, streaming data, phone calls, or other forms of communications.

In one example, the SLA guarantee for the four node configuration shown in FIG. 2 may be determined by taking the CIR throughput level to the customer represented by UNI 202, 1 Gig, and dividing by three (the customer cannot be in communication with itself) to determine the guaranteed CIR is approximately 333 Mb.

Based on new interconnection standards and network configurations using frame loss as a metric to determine an SLA guaranteed CIR is problematic because of potential communications between the UNIs 202, 204, 206, and 208. Similarly, testing SLA guarantees via the application of throughput stress testing to confirm a CIR may cause problems by breaking operational rules, disrupting live service traffic to any number of other customers, and potentially crashing applications or portions of the MEN 201. Typically, stress testing degrades the shared bandwidth of the service itself and may not capture transient defective states that may occur. An illustrative embodiment may be utilized to track throughput performance measurements that may alleviate the need for in-service traffic testing utilizing synthetic or test packets that do not represent normal network traffic.

In another embodiment, the system and methods described herein may be utilized to measure real-time, non-real-time, and test packets and traffic. Test packets may be sent to represent real-time and non-real-time packet communications. In one embodiment, a test packet may be generated for every 1000 real-time packets, representative of applications, such as VoIP or gaming. By sending the test packet for every 1000 real-time packets any number of measurements or determinations may be made or inferred about individual or collective devices, connections, or networks. In another embodiment, a test packet may be generated for every 2000 non-real time packets, representative of applications, such as browsing. In yet another embodiment, the test packet(s) or pattern may be run for every 1000 packets (real-time and non-real-time) sent through a UNI. Test packets may also be sent based on timing or other similar factors or conditions.

In one embodiment, the size of the test packet, frame, or pattern may be randomly selected. In another embodiment, the size of the test packet may correspond to the average size of packets sent through the network or device. For example, the average size of packets as measured by a counter or intelligent network device may be determined for generating the packet at the average size. The test packets may be utilized to determine or compile information regarding actual throughput, delay, actual line rate, frames per second, or other factors.

In one embodiment, in order to set a CIR frame loss rate level so that it may not indicate loss, the level may be set to a threshold in which no contention occurs on the UNI. For example, CIR=UNI bandwidth/(# nodes−1). In another embodiment, the CIR may be set so that it is no more than fifty percent of the service offered to the UNIs 202, 204, 206, and 208.

The bandwidth utilization or CIR utilization may be measured numerically or statistically for each potential communications path in the MEN for communication data. For example, throughput counters and frame loss indicators may monitor and record relevant information and performance metrics. The traffic may be measured utilizing any number of devices or applications that track, measure, and/or record network traffic measurements. Frame loss is only expected when the SLA limits are exceeded or UNI congestion occurs. For example, the UNI 206 may have a CIR of 100 Mb. No frame loss is expected if less than 100 Mb are received, if however, UNI 202 transmits 80 MB to UNI 206, UNI 204 broadcasts 40 Mb, and UNI 208 broadcasts 30 MB, the incoming bandwidth is 150 Mb exceeding the CIR of 100 Mb. As a result, frame loss is expected and the SLA is considered to be compliant despite the frame loss.

Second, the core of the MEN 201 itself may have a core CIR. Tracking frame loss rate between all UNIs 202, 204, 206, and 208 does indicate if congestion or faults are occurring at a UNI if the core has reached an SLA capacity. During the time frames when the service is running at full capacity frame loss rate becomes expected or is within SLA compliance or acceptable behavior. For example, the MEN 201 may have a core CIR of 800 Mb. If UNIs 202, 204, and 206 communicate 250 Mb and UNI 208 communicates at 200 Mb, the core CIR of 800 Mb is exceeded by 150 Mb and frame loss is determined to be acceptable. As a result, potential alarms are not generated and the communications service provider is determined to have not violated the SLA despite the frame loss. Tracking UNI congestion and core congestion through frame loss indicators and UNI states enable true SLA conformance measurements.

The examples given of 95% of CIR and 1% are illustrative thresholds, UNI 1 tracks TX, RX for itself (i.e., alarms on the RX of UNI 1). The measurements and calculation of throughput and frame loss may be accomplished using any suitable packet counter, network probe, analysis tool, which may be integrated with a UNI, router or other network node or be displayed in line with such a device.

FIG. 3 is a state diagram of SLA states in accordance with an illustrative embodiment. The state diagram 300 of FIG. 3 may be embodied or implemented in a chip or chipset, digital logic, fully programmable gate arrays, or an application for determining the status of an SLA. In one embodiment, FIG. 3 may be applicable to Scenario 1 described above. The state diagram 300 may include states 302, 304, and 306. Service providers, operators, customers, and other groups may need the ability to isolate states of the network. The states may be utilized to minimize service interruptions, repair times, and operational resources by detecting, diagnosing, localizing, and notifying network management systems of defects in order to take corrective actions appropriate to the type of defect.

The state diagrams of FIGS. 3 and 4 may be utilized at one or more nodes in a network to determine whether the SLA is being met and record live traffic throughput to capture applicable thresholds as frame loss begins to occur. In one embodiment, the receiving portion of the UNI or node may perform all determinations of SLA compliance. In another embodiment, the applicable states may be performed by a measurement information base (MIB). States 302, 304, and 306 may indicate an alarm state, suppress alarms or take one or more associated actions. The states may be utilized to dynamically determine usage and oversubscription information and profiles for traffic engineering and network management and design. The states may also be utilized to record and store network or UNI characteristics and performance information at the moment(s) the alarm state is triggered.

In state 302 and state 306, the SLA is in compliance. In state 304, the SLA is in non-compliance. In state 302, no frame loss occurs. The SLA may be considered to be compliant.

In state 304, frame loss occurs in excess of the frame loss permitted under the SLA and the UNI CIR is not exceeded. As a result, the SLA is considered to be non-compliant. The SLA is non-compliant because the CIR is not being exceeded by the customer, but yet there is still frame loss in excess of the frame loss permitted under the SLA that does not fall within the terms of the SLA. As a result, any number of alarms may be activated or asserted indicating frame loss for troubleshooting, diagnose, and other corrective actions.

In state 306, frame loss occurs in excess of the frame loss permitted under the SLA and at the same time, the UNI CIR is exceeded. State 306 is acceptable because the user has exceeded the bandwidth guaranteed to the user at the transmit or receive end of the customer port and as a result frame loss and non-compliance with the SLA is acceptable. During state 306, any number of alarms that may be activated due to frame loss may be ended or turned off because the UNI CIR is exceeded. The determinations of the alarm state utilizing states 302, 304, and 306 may be performed locally by a device or performance information may be communicated to a separate network device for determination and alarm state management and control.

FIG. 4 is a state diagram of SLA states in accordance with an illustrative embodiment. The state diagram of FIG. 4 may be implemented or function with other state diagrams, such as FIG. 3. The state diagram 400 may include states 402, 404, 406, and 408. In one embodiment, FIG. 4 may be applicable to Scenario 2 described above. In some cases, service providers do not provide broad guarantees for bandwidth. For example, the communications service provider may limit the SLA based on a leg CIR and a core CIR through the network. As previously described, in the state 402 no frame loss occurs in excess of the frame loss permitted under the SLA and the SLA is considered in compliance.

In state 404, frame loss occurs when the UNI CIR is not exceeded and/or when the core CIR is not exceeded. As a result, the SLA is considered noncompliant in state 404. Any number of alarms or indicators may be set or initiated in response to entering state 404.

In state 408, frame loss occurs in excess of the frame loss permitted under the SLA when the core CIR is exceeded, the SLA is determined to still be in compliance. In state 406, if frame loss occurs when the UNI CIR is exceeded, the SLA is determined to still be in compliance. During states 406 and 408, alarms, such as those activated for state 404, may be deactivated, cancelled, or disengaged because of the noncompliance with the SLA.

In one embodiment, the communications service provider may track the packets transmitted and received over the core network (all UNIs bundled together) between each UNI pair, and to each and from each UNI. Although not illustrated herein, the embodiments described in FIGS. 3 and 4 may be expanded to further consider whether or not the CIR of a remote node or UNI has been exceeded. If the CIR for such remote UNI have been exceeded, network performance measurements indicating a performance issue such as excessive frame loss that include the measurement of traffic to or from the remote UNI may also be permitted despite violating a particular service level because of the exceeded CIR.

For SLA compliance, a throughput SLA does not provide accurate information on SLA compliance. As a result, frame loss is still required as an important metric to determine compliance with the SLA requirements. Determining SLA compliance may be performed as described by the various illustrative embodiments.

Certain illustrative embodiments may allow a communications service provider or customer to measure metrics used to determine whether obligations are being met under an SLA. The proposed systems and methods do not require stress testing the network in order to determine SLA compliance. Additionally, certain illustrative embodiments may be utilized by network engineers to determine potential traffic and demonstrate compliance with SLAs when customers are operating within their CIRs. Additionally, communications service providers may use certain illustrative embodiments to ensure that they do not oversell bandwidth, legs, or the core user to provide their service.

Bandwidth

Throughput performance management rates are frequently discussed in terms of Ethernet frame octets received (EFOR) and Ethernet frame octets transmitted (EFOT). The throughput rate is the amount of EFOR and EFOT measured over a short time period. In one embodiment, the throughput rate may be measured with respect to the bits passing through a maintenance entity, network node, or Access Transport Resource Control Functional (A-TRCF) entity for the CIR, extended information rate (EIR), or both together as a single measure of throughput. Performance measurements, such as frame loss, may be calculated based on all network traffic or only based on conforming traffic, such as traffic that is within a customer CIR.

Ethernet has multiple standard frame sizes whereas asynchronous transfer mode (ATM) has one frame size. In one example, Ethernet frames may vary in size from 64 to 1,518 octets. This however, does not include 96,200 jumbo frames supported by Gig-E. Live Ethernet traffic includes mixed types of packet sizes with Voice over Internet Protocol (VoIP) packets generally being around 128 bytes, and Internet traffic being composed of both 64 byte and 1,518 byte packets. Given that the service blend of packets of differing size is dynamic and that differences may exceed two orders of magnitude, such frame loss as a performance indicator is inaccurate. The deviation in packet size makes using frames per second or frame rate measurements an invalid throughput indicator or performance measurement. Clock skew in Ethernet chips may also cause variations as high as 1% in the amount of frames that may be transmitted due to variations in frame gaps. Although not illustrated herein, the embodiments described in FIGS. 3 and 4 may be expanded to further consider whether or not the CIR of a remote node or UNI transmitting to the illustrated UNI has been exceeded. If the CIR for such remote UNI have been exceeded, network performance measurements indicating a performance issue such as excessive frame loss that include the measurement of traffic to or from the remote UNI may also be permitted despite violating a particular service level because of the exceeded CIR.

FIG. 5 is a pictorial representation of nodes in a network in accordance with an illustrative embodiment. FIG. 5 shows multiple nodes that may be included in a network. In one embodiment, the network may include node A 502, node B 504, node C 506, node D 508, node E 512, and node F 510. As previously described, the nodes may represent any number of UNIs, devices, components, equipment, ports, or constructs.

The nodes may both transmit and receive data to any of the other nodes as shown. As previously described, a network performance device or process may not be able to determine compliance with a SLA when multiple nodes communicate with a single node simultaneously. For example, node B 504, node C 506, and node D 508 transmit data to node E 512 at the same time utilizing a large amount of bandwidth that exceeds the terms of the SLA. Certain illustrative embodiments provide a system and method for compensating for the situations of FIGS. 5 and 7 without generating alarms, recording SLA violations or entering an error state.

FIG. 6 is a pictorial representation of a flowchart of a process for determining whether losses within a network comply with an SLA in accordance with an illustrative embodiment. The process of FIG. 6 may be implemented by a UNI or other node in accordance with an illustrative embodiment. Although specifically described for one node in an illustrative embodiment, the process of FIG. 6 may be performed for multiple UNIs.

The process may begin with a UNI or other device summing the bits received by node A from each of nodes B through F for a specified time interval (step 602). The nodes may represent UNIs communicating with the UNI being monitored, such as node A thereby establishing UNI pair Bt-Ar, Ct-Ar, Dt-Ar, Et-Ar, and Ft-Ar. The time interval may be any measure specified by the network administrator. In one embodiment, the time interval may be an amount less than 1 second. The measurement in step 602 measures the total amount of bits received by a node from all nodes within the network for such time interval. In one embodiment, the measurement or calculation of step 602 may be initiated in response to a determination that there is loss within the network or at the UNI being monitored.

Next, the UNI determines whether the sum of the summed bits is greater than a bandwidth profile for node A (step 604). The bandwidth profile may be specified by the SLA. For example, the bandwidth profile for node A may be included in a customer agreement with a communications service provider.

If the UNI determines that the sum of the summed bits is greater than a bandwidth profile or CIR for node A, the UNI may indicate or store an indication that the frame loss triggers a violation of the SLA (step 606). In one embodiment, the frame loss may trigger an obligation of the communications service provider. For example, the communications service provider may be required to provide a customer associated with the UNI a discount, credits, or remedy for the loss.

If the UNI determines that the sum is greater than a bandwidth profile or CIT for node A, the UNI may indicate that the frame loss is permitted and does not trigger a violation of the service level agreement because the bandwidth profile has been exceeded (step 608). Such indication may occur because multiple nodes are communicating with the UNI simultaneously in a manner that is not within a CIR or that is otherwise not supported by the SLA.

FIG. 7 is a pictorial representation of a network ring in accordance with an illustrative embodiment. FIG. 7 shows multiple nodes that may communicate through a ring 100 in a network. In one embodiment, the ring 100 may communicate with node A 702, node B 704, node C 706, node D 708, node E 712, and node F 710. As previously described, the nodes may represent any number of UNIs, devices, components, equipment, ports, or constructs. The ring 100 is the core of a network. The ring 100 is one embodiment of any number of topologies that may be utilized in a communications environment as all or a portion of a network. The ring 100 may include any number of interconnected devices, equipment, and systems. The nodes may communicate with the other nodes through the ring 100, as shown. As previously described, the ring 100 may not be able to determine compliance with a SLA for guaranteed core performance when multiple nodes communicate through the ring 100 at or near maximum capacity simultaneously. For example, if node B 704, node C 706, node D 708, and node E 712 transmit and receive data at their maximum bandwidth simultaneously, the terms of the core SLA may be exceeded. Certain illustrative embodiments provide a system and method for monitoring such situations without entering an error state.

FIG. 8 is a pictorial representation of a flowchart of a process for determining whether losses within a network comply with an SLA for core throughput in accordance with an illustrative embodiment. The process of FIG. 8 may be implemented by a UNI, application engine within a server, or other element of a communications management system. Although specifically described for one node, in an illustrative embodiment, the process of FIG. 8 may be performed for multiple nodes or UNIs simultaneously.

The process may begin by summing the bits received by UNI A from each node B_(t), C_(t), D_(t), E_(t), and F_(t) comprising five nod pairs through a ring over a particular time interval (step 802). The pairs may represent all UNIs communicating directly with the UNI being monitored, such as UNI A. The time interval may be any measure specified by the network administrator. In one embodiment, the time interval may be an amount less than 5 seconds. The measurement in step 802 measures the total amount of bits received by UNI A from nodes within the network for the time period. In one embodiment, the measurement or calculation of step 802 may be initiated in response to a determination that there is frame or packet loss within the network or at the UNI being monitored, network congestion, or other network issues.

Next, the UNI determines whether the sum is greater than a bandwidth profile for the ring (step 804). The bandwidth or throughput profile may be specified by the SLA. For example, UNI A may represent a UNI of a customer that has an agreement with a communications service provider for core bandwidth through a ring or core portion of the network.

If the UNI determines that the sum is not greater than a bandwidth profile for the ring, the UNI records that any loss is accounted for based on the SLA. (step 806). In one embodiment, the loss may be required to be accounted for by the communications service provider. For example, the communications service provider may be required to provide a customer associated with the UNI a discount, credits, or retribution for the loss.

If the UNI determines the sum is greater than a bandwidth profile for the ring, the UNI records that the loss is normal and not recorded against the SLA because the bandwidth profile for the network core is exceeded (step 808). The recordation of step 808 indicates that the loss is occurring because multiple UNIs are communicating through the ring simultaneously in a manner that is unsustainable and not supported by the SLA. For example, the core bandwidth of the ring may be one gigabyte and may be exceeded by four UNIs simultaneously transmitting (or attempting to transmit) at 500 Mb.

Another matter complicating the issue of determining if a frame loss occurrence is normally expected is the use of a bit-based rate limiter or shaper at one end of a path and a physical UNI port at the opposite end. Rate limiters enforce bandwidth profiles based upon bit rates and not frame sizes. UNI ports, however, have a frame size dependant bandwidth profile that limits the amount of “effective” bit throughput that may be transmitted through the port at any given time. This relationship is caused due to the “cell tax” or inter-frame-gap (IFG) and inter-frame-overhead, and other frame components, such as the start frame delimiter (SFD), that are not counted by bit based rate shapers. The end result of the UNI bandwidth profile is that for every frame per second transmitted through a UNI the “cell tax” overhead of the IFG, and other non-bits are subtracted from the UNI line rate. This relationship results in small frames having less “effective” throughput or bit based throughput than large frames. However, rate shapers and rate limiters do not change their bandwidth profile with frame size as do UNI ports. This causes a mismatch in the bit based rate limiter to frames size dependant throughput profile of a port. In one embodiment, when a rate limiter uses a 76.2% or higher bandwidth profile of the UNI port line rate frame loss may occur because of the frame size dependency at the UNI port. To account for frame size, a frame per second dynamic bandwidth profile tool may be required to decipher if the bandwidth loss was caused by the bandwidth profile mismatch of a rate limiter to the UNI, which is frame size dependant.

FIG. 9 is a pictorial representation of a network performance system in accordance with an illustrative embodiment. In one embodiment, the network performance system 900 of FIG. 9 may be encompassed in a device, such as a UNI. A network performance system 900 may include or perform basic measurements, derived calculations, and threshold crossings. The elements may be circuits, logic, or hardware or may include a program, instructions, or stored elements. FIG. 9 may further include one or more interfaces communicating with a number of rate limiters, policers rate shapers, or network modules. FIG. 9 may also be utilized to perform the other methods and processes herein described. In one embodiment, the network performance system 900 may include alarms 902, performance logic 904, SLA module 906, dynamic bandwidth profile 908, and logic 910 and 912.

The alarms 902 represent service or system messages alerts that may be generated in response to the rules of SLA module 906 being violated based on the dynamic bandwidth profile 904 (and associated thresholds) as determined by the performance logic 904. The message or alarm may include a variety of information, factors and network conditions measured, calculated, or inferred including: maximum throughput (including effective and instantaneous rates), measured throughput, maximum frames per second, measured frames per second, loss, compliance with the SLA, packet size, average packet size, total available bandwidth, thresholds, physical line rate, measured line rates (instantaneous and effective). The performance logic 904 is the circuits, instructions, and other intelligent components operable to determine whether the service level agreement has been violated utilizing a static bandwidth profile or the dynamic bandwidth profile 908. The SLA module 906 may utilize rules based on any number of states, steps, or processes as previously described in FIGS. 3-8.

The dynamic bandwidth threshold 908 may act to regulate a policing function or policer by providing feedback that may be utilized to reduce throughput limits (i.e. based on frame size and frames per second). The dynamic bandwidth threshold may simply be used to gauge if a rate limiter failed to enforce a small frame bandwidth profile, which was discarded by a UNI port. The dynamic bandwidth profile 908 may be applicable to ports or devices. The dynamic bandwidth profile 908 may utilize logic 910 or logic 912. Logic 910 indicates the maximum instantaneous throughput rate based on a frame rate in terms of a threshold that may be utilized to determine compliance with an SLA. Logic 912 indicates the instantaneous line throughput rate as compared to the capabilities and capacity of the physical line rate. Either logic 910 or 912 may be utilized to determine compliance with an SLA utilizing throughput ranges and thresholds in terms of payload or line rate (logic 910 or 912, respectively). The throughput ranges specify minimum and maximum throughput levels or thresholds based on frame sizes of packets communicated. The throughput ranges may be incorporated within the SLA negotiated between a service provider or company. Alternatively, the SLA may be incorporated in a customized application with terms, thresholds and parameters, that are individually determined. For example, the minimum value of the throughput range may be much lower for small packets than for large packets because of the introduction of overhead. The maximum instantaneous throughput rate and the instantaneous line throughput rate may also be referred to as the “maximum throughput.”

The logic 910 and 912 may be utilized in response to determining there is packet loss to determine compliance or non-compliance with terms of the SLA particularly relating to throughput or lines rates. Compliance with the SLA incorporates acceptable ranges based on inter-frame overhead, skew, packet or frame size, and similar factors. Logic 910 and 912 provide utilization information in terms of effective throughput rate or line rate.

In one embodiment, the dynamic bandwidth profile 908 may establish the maximum effective transmission rate based upon the UNI port's maximum frames per second at the largest and smallest maximum transmission unit (MTU) size, and the corresponding effective throughput rate for that MTU size and frame rate.

In a second embodiment, the dynamic bandwidth profile may be based upon the UNI line rate, and the frames per second measure, with the corresponding frame overhead or “non-bit” counted portions of each frame. For example, the dynamic bandwidth profile 908 may be utilized to determine if the traffic present conforms with the frame based throughput of the port rather than a static bandwidth profile. The dynamic bandwidth profile 908 may utilize measurements from the bit-based throughput counters of the network to determine compliance. Compliance with throughput levels may be determined in response to the dynamic bandwidth profile 908 being between 76.2% and 100% of the port line rate speed. The relevant speeds and percentages may be determined based on industry standard inter-frame-gap and “non-bit” overhead, such as SFD.

An example may be utilized to explain logic 910. In an illustrative embodiment, a single circuit with a Gig-E may be located at one end, and a 100 Mb Fast Ethernet port may be located at the second end. The service may be a 100 Mb service with a “rate-limiter” at the Gig-E end. In effect, the rate limiter will pass 100 Mbs of effective throughput. However, with small packets, such as 64 byte frames, only 76.2 Mbs of payload may fit inside of the 100 Mb line rate port due to the percentage of overhead. However, 99.8 Mbs of 1581 byte frames will fit into the port due to a lower ratio of overhead to payload.

The rate limiter is typically a bit based effective throughput bandwidth profile and may not be constrained by a line rate, and as a result, may allow too many small frames through the service. As a result, the small frames may be dropped at the far end when the frames attempt to enter the UNI or 100 Mb Fast Ethernet port.

A dynamic frames per second “threshold” may be required to identify if the line rate of the frames being transmitted exceeded the bandwidth profile of the UNI port. Given that the frame bit counters commonly used by packet systems do not typically use a line rate, logic, an equation, algorithm, or other instructions may convert the instantaneous bandwidth (during a short time period) to a line rate that may be used to determine if the effective throughput may be communicated through the port or is less than the port speed.

The logic 912 may be utilized to convert the effective bandwidth to a line rate. If the effective bandwidth rate exceeds the UNI port line rate, the frame loss is not counted because those frames exceeded the UNI port rate (line rate, e.g., 100 Mbs). Normally, the effective throughput measurement does not detect such conditions.

The logic 912 may utilize a “static UNI line rate threshold” to determine if the throughput allowed by the rate limiter was or was not service conforming (able to be communicated through the UNI port). The logic 912 may utilize the instantaneous throughput determined by the bit counters and add the overhead of the IFG to the effective throughput to adjust to a line rate utilization. The line rate utilization is then compared to the line rate. If the line rate utilization is above the port's line rate, the traffic does not conform to the service. If the value was below the line rate (100 Mb), then the traffic did conform and the loss should not have occurred.

The following provides additional details and embodiments for the logic 910 and/or 912. In one embodiment, the dynamic bandwidth profile 908 may determine the throughput rate of a port. The throughput rate may be determined to be less than or equal to a determination of parameters. In one embodiment, the parameters may include effect throughput rate, port speed, the frames per second, and the inter-frame overhead. In many cases, packet technologies are non-synchronous and use inter-packet or inter-frame gap with a “start of frame” bit pattern to signal that the information that follows is a packet. Inter-frame gap as well as frame and packet sizes may vary the throughput potential of communications devices, systems, and links dependant upon packet size.

Throughput is dependent on frame size and may change as the frame size changes dynamically. As a result, packet service level capacities are often stated in terms of the throughput rate of the MTU size or frame size. For example, 90 Mbs with 1518 byte frames is a statement of throughput rate. However, the use of smaller frames yields less throughput of the frame payload. In one ongoing example, 64 bytes have a throughput capacity of 76.2 Megs for a 100 Megabyte port. In effect, every time a frame is added for a given time period, the size of the overhead and non-payload bits relative to the overall frame size also increases.

Therefore, the maximum MTU throughput rate minus the added incremental frames per second multiplied by the inter-frame overhead yields the instantaneous dynamic effective throughput capacity. Such logic may be expressed by subtracting the current frame per second interval from the fastest rate that frames may be sent per second for the maximum MTU size multiplied by the inter frame overhead and then subtracting that value from the maximum MTU size effective throughput. The result is a threshold that indicates the amount of payload or effective bits that may pass through the service based on the loss of throughput due to the added frames per second overhead.

For example, the dynamic bandwidth profile 908 may be utilized to determine that the actual effective frame per second dependant bandwidth profile 910 is 76.2% of service payload utilizing 64 byte packets and 99.8% of service payload with 1518 byte packets. As a result, the systems, devices, user, or equipment may account for the potential 24% of overhead by adjusting line rates and throughput levels. The dynamic bandwidth profile 908 may ensure that frame loss does not occur between a UNI-N and a UNI-C.

Example 1 and 2 provided below provide more specific examples of implementation of the logic 910 and 912 (sample values for each parameter are also illustrated in FIGS. 10 and 11).

EXAMPLE 1

For a nominal port speed (100 Mb for a Fast Ethernet port) MDT _(FPS) ≦MTUTP _(max)−[(FPS _(c) −FPS _(MMTU))*OHB]

MDT_(FPS)=Maximum Dynamic throughput in Frames per Second

MTUTP_(max)=Max. MTU Size maximum Effective throughput

FPS_(c)=Current Frames per Second (during a time interval that the throughput is checked)

FPS_(MMTU)=Max MTU size, Max. Frames per Second (highest rate they can be sent)

OHB=bits of Overhead introduced with each frame (taken away from max effective throughput).

EXAMPLE 2

For Ethernet one embodiment works as follows: MDT _(FPS) ≦MTUTP _(max)−[(FPS _(c) −FPS _(MMTU))*OHB] For a Fast Ethernet Port/or 100 Megabit Ethernet Service with a Maximum frame size (MTU) of 1518 bytes.

MDT_(FPS)=Max. achievable bandwidth at that # of frames

MTUTP_(max)=99.80 Megabytes

FPS_(c)=X−current interval # of frames

FPS_(MMTU)=8,127

OHB=0.00016

MDT_(FPS)≦98−[(FPS_(c)−8,127)*0.00016]

Reference to frame size or packet size may refer to an average value that is calculated for a time period or amount of data with the calculations being adjusted. The average value for packet or frame size may also be rounded up or down as needed to meet communications standards and protocols.

The instantaneous line throughput rate corresponds to the line rate utilization subsequently described. The instantaneous effective throughput rate corresponds to the effective throughput as further described. As discussed, the time period may be adjusted for the logic 912 for a small time period (10 ms) that is a nearly “instantaneous” determination of the line rate utilization to a larger time period (3 s) that provides a more long term or stable snapshot of the data stream.

FIGS. 10 and 11 are pictorial representation of bandwidth tables 1000 and 1100 in accordance with illustrative embodiments. The bandwidth tables 1000 and 1100 provide examples of data that affect the bandwidth at a UNI or within a network as influenced by frame size, as described herein. In one embodiment, the tables 1000 and 1100 may be stored in electronic form in a UNI or in a database in order to determine compliance with an SLA. For example, compliance with the SLA may be determined dynamically utilizing the thresholds, ranges, values, and factors included in or derived from the bandwidth tables 1000 and 1100.

FIG. 12 is a pictorial representation of a portion of a data stream in accordance with an illustrative embodiment. Data 1200 shown in FIG. 12 may be communicated in a data stream or other data flow. The data 1200 may include at least a frame 1202 and overhead 1204.

In one embodiment, the frame 1202 may include bytes indicating a destination address, sources address, length/type of frame, a payload, and a frame check sequence of each which may include various bytes as illustrated by the data 1200. The frame 1202 includes the bits that may be typically counted as an effective throughput, such as the payload. For example, a counter in a communications device may measure the size of the frame 1202 when reporting on throughput.

The overhead 1204 may be the separation data and information associated with a communication, such as the data stream. In one embodiment, the overhead 1204 may include the inter-frame gap, a preamble with a start of frame delimiter (SFD), and/or encapsulation. Data Encapsulation is a process of taking one protocol data unit (PDU) and enveloping the PDU within a protocol header and/or trailer. For example, encapsulation may include the header for the frame 1202. Segmentation, recombination, or emulation overhead may also be included. The various types of overhead may include capacity limits and may not be visible due to being removed prior to the data stream encountering the specific data counters. Capacity limits may be the line rate bits per second capacity of the physical media, such as a port or RF channel. Segmentation and recombination may be used by a protocol or router when passing large frames over a protocol, network, system, or device that uses smaller frames. For example, segmentation and recombination (SAR) is utilized to interface protocols, such as asynchronous transfer mode (ATM) and internet protocol (IP), resulting in additional overhead based on decreased efficiency. Emulation may allow different protocols to emulate an established protocol for purposes of sending uniform communications. For example, emulation overhead may allow bandwidth measurement techniques for IP or ATM traffic to be applied to different types of signaling, such as an RF channel or a time division multiple access (TDMA) signaling.

In existing systems, the overhead 1204 is not measured by the counter when measuring throughput. As a result, a large number of bytes may not be tracked during communications. Measuring and tracking the overhead 1204 is even more important when the size of the frame 1202 is small, thereby increasing the percentage of the data stream required to communicate overhead 1204 between each frame. Even though the size of the overhead 1204 may be consistent, more smaller frames means that an increasing number of overhead bytes separates each frame. In one embodiment, the overhead 1204 may be equal for each frame specified by the applicable communications standard or protocol. The frame 1204 may vary in size, particularly, depending on the payload. The overhead 1204 size may be utilized as a constant for determining the line rate utilization. The determination of the line rate utilization associated with the frame 1204 and overhead 1204 may be used to determine compliance with physical capabilities of the network element, such as the port. For example, the line rate utilization may indicate whether a maximum transmission speed of the port is violated.

In one embodiment, the overhead 1204 attributes are stored as bits or octets in a network element. For example, the overhead 1204 may be set as 20 bytes between frames as a port attribute for determining the line rate utilization based on the frames communicated per second or other time period. The overhead 1204 may then be referenced when determining the line rate utilization.

FIG. 13 is a graph 1300 illustrating throughput based on frame size in accordance with an illustrative embodiment. The graph 1300 may measure theoretical calculations of the maximum effective throughput or the line rate utilization measured across a connection, port, or device. The x axis 1302 of the graph illustrates frame size in bytes. The y axis 1304 of the graph 1300 illustrates the throughput in megabits per second. The maximum effective throughput increases as the frame size increases because the percentage of overhead as compared to the overall data stream is reduced. As the graph 1300 illustrates, the maximum effective throughput begins to decrease dramatically once the frame size drops below approximately 500 bytes. The percentage of the data stream occupied by overhead increases as the frame size decreases resulting in reduced maximum effective throughput.

In one example, the graph 1300 may represent a port of a UNI capable of communicating at 100 Mb/s or 100% of the line rate. The line rate utilization actually ranges from 76.2% of the line rate for 64 byte frames to 98.0% for 1518 byte frames due to the amount of overhead introduced by each frame size. In some cases, the variance between effective throughput rate measured by counters and the line rate utilization (which includes overhead) that is communicated through devices and connections may confuse users. Users that are paying to access services may have no idea how to determine the maximum effective throughput based on frame size and the other factors herein described. As a result, policers, shapers, ports, or other network elements may configure traffic utilizing the described determinations that include overhead in addition to payload, which is a more accurate measurement of total data communicated through the data stream

FIG. 14 is a flowchart of a process for determining line rate utilization in accordance with an illustrative embodiment. In one embodiment, the process of FIG. 14 may be implemented by a port or port counter of a communications device. The port may utilize specially configured counters, logic, or applications executed by a processor to determine the line rate utilization as shown by FIG. 14 and the logic 912 of FIG. 9 (Line Rate Utilization=(Effective throughput rate+(Frames per second*(frame overhead)))). For example, the ports may utilize traffic at a virtual local area network (VLAN) level or switch monitoring (SMON) level.

The process may begin with the port measuring an effective throughput for a data stream (step 1402). Step 1402 may be performed using standard processes for measuring throughput.

Next, the port counts the number of frames in the data stream (step 1404). In one embodiment, the port may utilize the frame check sequence to distinguish between frames. Next, the port determines whether a time period has expired (step 1406). In one embodiment, the frames may be counted for a specific time period that functions as a sampling time period. For example, the time period may be one second or three seconds. The time period may be configurable based on user requirements, information requests from other devices, or other factors or criteria.

Next, the port determines a line rate utilization for the data stream utilizing the number of frames and the size of the frames (step 1408). The number of frames and the size of the frames may dramatically affect the overhead and line rate utilization as shown in the graph 1300 of FIG. 13. Even though the size of the overhead may be known, the frame size may be determined by the port to determine the line rate utilization. In many cases, standard minimal inter-frame gaps are typically port-based. The number of bits included in a gap between frames on a Fast Ethernet port (100 megabits per second) may not be the same amount of bits as the inter-frame-gap on a Gig-E port (1000 megabits per second). Therefore, when a mixed physical port circuit is used with a Gig-E port on one end, and a Fast Ethernet port on the other end, the line rate of each is different given that overheads or gaps are not equivalent. To accommodate this difference, the amount of overhead may be a settable attribute for each direction of the service.

In one embodiment, the components of the frame and overhead may be measured in bytes or octets that require conversion to bits for displaying the information or data in a standard format. The port converts bytes to bits and outputs the line rate utilization (step 1410). In one embodiment, the port may save the line rate utilization, information about the data stream, and/or other network conditions for the time period to a database or memory. This information may be utilized to determine why or how the line rate utilization exceeded a maximum throughput of the network, device, system, or interface. In another embodiment, the port may immediately communicate the line rate utilization to one or more users, electronic devices or other elements for storage, archival, or real-time display. As used herein, users may represent users, services providers, devices, applications, parties, individuals, organizations, or other electronic elements.

The port then resets the time period (step 1412) before returning to measure an effective throughput for a data stream (step 1402). The process of FIG. 14 may be repeated to constantly provide users, devices, and applications accurate determinations of the line utilization rate for policing, shaping, configuring network systems and devices, and

The illustrative embodiments provide a system and method for determining the maximum throughput and measuring the line rate utilization in real time. The line rate utilization may be used as a metric for all layers of the OSI model. In one embodiment, the line rate utilization may be communicated to one or more users, such as customers, network operators, network engineers, and service providers. The line rate utilization may be utilized to reconfigure devices, suppress or generate alarms, record network conditions, or otherwise monitor, measure, and reconfigure network conditions. The line rate utilization metric may be used for determining and controlling capacity, utilization, and throughput system feedback for individual devices, systems or all or portions of a network.

The previous detailed description is of a small number of embodiments for implementing the invention and is not intended to be limiting in scope. The following claims set forth a number of the embodiments of the invention disclosed with greater particularity. 

What is claimed:
 1. A method for tracking a line rate utilization, the method comprising: measuring an effective throughput for a data stream during a time period; counting a number of frames in the data stream during the time period; determining a line rate utilization for the data stream utilizing the number of frames and a size of the frames in response to the time period ending, wherein determining the line rate utilization is performed by taking the number of frames communicated during the time period multiplied by frame overhead and adding it to the effective throughput; saving the line rate utilization for communication to one or more users; and communicating the line rate utilization to one or more users.
 2. The method of claim 1, further comprising: determining compliance with a service level agreement (SLA) in response to comparing the line rate utilization and a maximum line rate.
 3. The method of claim 1, wherein the measuring, counting, determining, saving, and communicating is performed by a port of a communications device.
 4. The method of claim 1, further comprising: converting the line rate utilization into a bits measurement from a bytes measurement associated with the size of the frames.
 5. The method according to claim 1, further comprising: resetting the time period in response to communicating the line rate utilization to one or more users.
 6. The method according to claim 1, further comprising: dynamically determining compliance with a service level agreement (SLA) in response to thresholds associated with frame size; and reporting compliance with the SLA in a message, the message including network conditions at the time of the message.
 7. The method according to claim 6, further comprising: communicating SLA compliance in the message, the SLA including a throughput range associated with potential frame sizes communicated through a user network interface (UNI).
 8. The method according to claim 3, further comprising: rate limiting packets communicated through the port in response to the line rate utilization.
 9. The method according to claim 1, wherein the frame overhead is set based on a communications standard or protocol utilized for the data stream, wherein frame overhead is set as an attribute of a network element, wherein the line rate utilization is communicated to a plurality of network devices to adjust traffic to keep the data stream below a maximum line rate.
 10. The method according to claim 1, wherein communicating the line rate utilization includes communicating a message indicating a maximum line rate and the line rate utilization in response to determining there is loss.
 11. The method according to claim 1, wherein communicating the line rate utilization includes an alarm generated in response to violation of an SLA.
 12. A system for tracking a line rate utilization, the system comprising: a user network interface (UNI) operable to communicate with a plurality of UNIs; a network operable to communicate packets between the UNI and the plurality of UNIs; and wherein the UNI includes a port operable to: measure an effective throughput for a data stream during a time period; count a number of frames in the data stream during the time period; determine a line rate utilization for the data stream utilizing the number of frames and a size of the frames in response to the time period ending, wherein determining the line rate utilization is performed by taking the number of frames communicated during the time period multiplied by frame overhead and adding it to the effective throughput; save the line rate utilization for communication to one or more users; and communicate the line rate utilization to one or more users.
 13. The system according to claim 12, a rate limiter for shaping packet traffic, the rate limiter limiting the packets communicated in the network in response to a comparison of the line rate utilization and a maximum line rate.
 14. The system according to claim 12, wherein the port dynamically determines compliance with an SLA utilizing one or more thresholds for throughput and the line rate utilization.
 15. The system according to claim 14, wherein the frame overhead is set based on a communications standard or protocol utilized for the data stream, wherein frame overhead is set as an attribute of a network element, wherein the port is further operable to convert the line rate utilization into a bits measurement from a bytes measurement associated with the size of the frames for communication to the one or more users and reset the time period in response to communicating the line rate utilization to one or more users.
 16. A port operable to track a line rate utilization, comprising: a processor for executing a set of instructions; and a memory in communication with the processor, the memory operable to store the set of instructions, wherein the set of instructions are executed to: measure an effective throughput for a data stream during a time period; count a number of frames in the data stream during the time period; determine a line rate utilization for the data stream utilizing the number of frames and a size of the frames in response to the time period ending, wherein determining the line rate utilization is performed by taking the number of frames communicated during the time period multiplied by frame overhead and adding it to the effective throughput; save the line rate utilization for communication to one or more users; and communicate the line rate utilization to one or more users.
 17. The port according to claim 16, wherein the port is integrated with a network communications device, the port is operable to communicate the line rate utilization to one or more users through one or more network connections.
 18. The port according to claim 16, further comprising: dynamically determining compliance with a SLA or technical threshold in response to the line rate utilization.
 19. The port according to claim 18, wherein the frame overhead is set based on a communications standard or protocol utilized for the data stream, wherein frame overhead is set as an attribute of a network element, wherein the set of instructions are further executed to convert the line rate utilization into a bits measurement from a bytes measurement associated with the size of the frames for communication to the one or more users and reset the time period in response to communicating the line rate utilization to one or more users. 